ci: build and publish Windows release on merge to main - #3
Merged
Conversation
Add a GitHub Actions workflow that compiles the game with MinGW-w64 on a Windows runner, packages SpaceDefender.exe together with openal32.dll and the ressources/ folder, and publishes the archive as a GitHub Release. - push to main: build + publish release v1.0.<run_number> - pull_request to main: build only, archive kept as a CI artifact - workflow_dispatch: manual run MSYS2 is used with release: false so the toolchain lives at C:/msys64, the path CMakeLists.txt hardcodes for WIN32 builds.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a GitHub Actions workflow that compiles the game with MinGW-w64 on a Windows runner, packages SpaceDefender.exe together with openal32.dll and the ressources/ folder, and publishes the archive as a GitHub Release.
MSYS2 is used with release: false so the toolchain lives at C:/msys64, the path CMakeLists.txt hardcodes for WIN32 builds.